Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1033

reference: 266-tree-1
name: 1033
tree-preservation-order: undefined
266-tpo-1
uprn
address-text
point: POINT (-0.937981 50.858813)
geometry: MULTIPOLYGON (((-0.937925 50.858807,-0.937927 50.858818,-0.937935 50.858828,-0.937947 50.858836,-0.937963 50.858841,-0.937981 50.858843,-0.937998 50.858842,-0.938014 50.858837,-0.938027 50.858829,-0.938035 50.858819,-0.938038 50.858808,-0.938036 50.858797,-0.938028 50.858787,-0.938016 50.858778,-0.938000 50.858773,-0.937982 50.858771,-0.937965 50.858773,-0.937949 50.858778,-0.937936 50.858786,-0.937928 50.858796,-0.937925 50.858807)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL